Pdcp count handling in rrc connection resume

ABSTRACT

Methods and apparatus, including computer program products, are provided for resuming connections. In some example embodiments, there may be provided a method that includes receiving, at a user equipment, a radio resource control connection resume message; verifying, at the user equipment, an integrity of the received radio resource control connection resume message, wherein the user equipment verifies the integrity based on a predetermined value of a packet data convergence protocol hyper frame number; and resuming, by the user equipment, use of a suspended radio resource control connection, when the integrity verification of the received radio resource connection resume message is passed successfully. Related systems, methods, and articles of manufacture are also described.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and the benefit of U.S. Provisional Patent Application No. 62/394,057 which is entitled “PDCP COUNT HANDLING IN RRC CONNECTION RESUME,” and filed on Sep. 13, 2016 (attorney docket: 49700-190P01US), 2016, the disclosure of which is incorporated herein by reference for all purposes.

FIELD

The subject matter described herein relates wireless.

BACKGROUND

User equipment (UE), such as a smartphone, a cell phone, an Internet of Things (IoT) device, and/or other type of wireless apparatus accessing a radio access network including a base station, may suspend a connection, and then resume the connection at a later time. For example, a radio resource control (RRC) connection may be suspended between the UE and base station. When this is the case, some of the communications, such as user plane traffic between the user equipment and the base station, may be suspended. However, the UE and the base station may maintain the context of the connection, so that the UE and base station can quickly resume the RRC connection using the prior context, without having to create an entirely new RRC connection. The context may include the radio bearer configuration information, security parameters, cell identifiers, physical layer configuration information, measurement and reporting configuration information, and/or the like. Examples of connection suspension and resume of RRC connections can be found in TS 36.331. See, e.g., 3GPP TS 36.331 V13.2.0 (2016-06), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification, Release 13.

SUMMARY

Methods and apparatus, including computer program products, are provided for resuming connections.

In some example embodiments, there may be provided a method that includes receiving, at a user equipment, a radio resource control connection resume message; verifying, at the user equipment, an integrity of the received radio resource control connection resume message, wherein the user equipment verifies the integrity based on a predetermined value of a packet data convergence protocol hyper frame number; and resuming, by the user equipment, use of a suspended radio resource control connection, when the integrity verification of the received radio resource connection resume message is passed successfully.

In some variations, one or more of the features disclosed herein including the following features could optionally be included in any feasible combination. A radio resource control connection resume complete message may be transmitted when resuming use of the suspended connection. The predetermined value may be fixed to enable synchronization between the user equipment and the base station. The predetermined value may include all bits set to a value of 1. The use of the suspended radio resource control connection may be resumed only when the integrity verification of the received radio resource connection resume message is passed successfully. The base station may be different than the base station where the user equipment suspended the radio resource control.

In some example embodiments, there may be provided a method that includes receiving, at a base station, a radio resource control connection resume request message sent by a user equipment; generating, in response to the received radio resource control connection resume request message, a radio resource control connection resume message; performing integrity protection of the radio resource connection resume message, wherein the integrity protection is performed based on a predetermined value of a packet data convergence protocol hyper frame number; and transmitting to the user equipment the radio resource control connection resume message, wherein the radio resource control connection resume message is integrity protected.

In some variations, one or more of the features disclosed herein including the following features could optionally be included in any feasible combination. The radio resource control connection resume request message may be received to enable resumption of a suspended radio resource control connection. The predetermined value may be fixed to enable synchronization between the user equipment and the base station. The predetermined value may include all bits set to a value of 1. The base station may be different than the base station where the user equipment suspended the radio resource control.

The above-noted aspects and features may be implemented in systems, apparatus, methods, and/or articles depending on the desired configuration. The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the description below. Features and advantages of the subject matter described herein will be apparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

In the drawings,

FIG. 1 depicts an example of a process for suspending and resuming a connection, in accordance with some example embodiments;

FIG. 2A depicts another example of a process for suspending and resuming a connection, in accordance with some example embodiments;

FIG. 2B depicts an example of a PDCP COUNT, in accordance with some example embodiments;

FIG. 3 depicts yet another example of a process for suspending and resuming a connection, in accordance with some example embodiments; and

FIG. 4 depicts an example of an apparatus, in accordance with some example embodiments.

Like labels are used to refer to same or similar items in the drawings.

DETAILED DESCRIPTION

The RRC connection may, as noted, be suspended by a user equipment and a network and resumed quickly by re-instating the RRC connection using prior, stored context information. When the RRC connection is suspended, this may also trigger the suspension of user plane traffic transfer, such as the PDCP (packet data convergence protocol) protocol data unit (PDU) transfer. The PDCP may provide one or more services to the RRC. These services may include control plane data transfer (via the uplink and/or downlink, for example), ciphering, and/or integrity protection. The PDCP may be implemented in accordance with a standard, such as TS 36.323. See, e.g., 3GPP TS 36.323 V13.2.0 (2016-06), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification (Release 13).

However, there may be certain problems with the RRC connection resume when a user equipment moves to another base station (“new base station”) different from the old base station where the RRC connection was suspended. During the resume, the user equipment and the old base station may have stored context information but the new base station may not have certain portions of the context information to properly resume the RRC connection. Specifically, the new base station may not have the correct last PDCP COUNT (e.g., the count or sequence number of the last PDCP packet data unit (PDU)). When this is the case, the UE may not be able to resume the connection since a lack of synchronization in PDCP COUNT between the UE and new base station may result in a failure of the integrity verification. This failure triggers leaving (as shown in Table 1 below which is reproduced from TS 36.331) the suspended RRC connection and the establishment of a new RRC connection.

TS 36.323 describes an example implementation of the PDCP COUNT comprising the PDCP sequence number (PDCP SN) and a hyper frame number (HFN), although other implementations of the PDCP COUNT may be used as well. To limit signaling overhead, individual messages/packets (which may be sent between the UE and base station) may include a short sequence number (PDCP SN), rather than the longer 32-bit PDCP COUNT (in which case the HFN would be synchronized between the base station and UE).

Regarding the PDCP COUNT, it may be implemented in accordance with TS.36.323. When this is the case, for each radio bearer, an independent counter, such as PDCP COUNT (which may be specified by TS 36.323) may be maintained for each of the uplink and the downlink. For each data radio bearer (DRB), the PDCP COUNT may be used as input for the ciphering, while for each signaling radio bearer (SRB), the PDCP COUNT may be used for both ciphering and integrity protection. At connection resume, the PDCP COUNT may be reset for PDUs exchanged after a RRC connection resume.

Given that the PDCP COUNT can wrap or rollover, the same PDCP COUNT value may not, however, be used more than once for a given security key. For example, the base station may be responsible for avoiding re-use of the same PDCP COUNT value with the same radio bearer identity and the same key, KeNB. To avoid the re-use, the base station may trigger an intra cell handover or perform another action that renegotiates the key.

TABLE 1 Reception of the RRCConnectionResume by the UE  The UE shall:  <...>  1> restore the PDCP state and re-establish PDCP entities for all SRBs and DRBs;  <...>  1> request lower layers to verify the integrity protection of the RRCConnectionResume message, using the previously configured algorithm and the K_(RRCint) key;  1> if the integrity protection check of the RRCConnectionResume message fails:  2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’, upon which the procedure ends;

In some example embodiments, PDCP COUNT synchronization may be provided between the UE and the base station during a RRC connection suspension and resumption, regardless of whether the RRC connection is resumed at the same, old base station where the RRC connection was suspended or another, new base station different from the so-called old base station. In some example embodiments, the PDCP COUNT synchronization is performed using a predetermined value.

In some example embodiments, at least part of the PDCP COUNT value used in integrity protection and verification of the RRCConnectionResume message may be specified as a fixed, predetermined value.

In some example embodiments, the HFN part of the PDCP COUNT may be configured to a fixed, predetermined value. This fixed value may have all bits set to “1”. After a PDCP re-establishment is invoked (which may be triggered by the RRCConnectionResume), the UE's PDCP will expect the next PDU received on an SRB to have a PDCP COUNT equal to zero, which is the next value in the PDCP COUNT after the PDCP COUNT value of 2³²−1. Having the fixed HFN part of the PDCP COUNT value predetermined to have all bits set to “1” may maximize the time until that fixed HFN part of the PDCP COUNT value would need to be used again with the same key (as well as other connection parameters) on the SRB. Repeated use of a previous COUNT value should be avoided in order to reduce the need to trigger a connection reestablishment as noted above. Although the same PDCP COUNT value with the fixed HFN part may have been previously used on the SRB at the base station (under which the UE's RRC connection was suspended), that prior use of the PDCP COUNT does not require a reset of the RRC connection due to integrity protection because the RRCConnectionResume message is already processed using a new security key. In some implementations, the PDCP SN may also be fixed (e.g., to have all bits set to “0” or all bits set to “1”).

FIG. 1 depicts an example of a process 100 for handling PDCP COUNT, in accordance with some example embodiments. The process depicts a user equipment 105 and a base station 110, such as an evolved node B type base station (eNB) although other types of base stations and wireless access points may be used as well.

At 112, the RRC connection may be suspended, in accordance with some example embodiments. When this is the case, user plane traffic transmission via the uplink and/or the downlink may also be suspended. Moreover, the UE 105 and the base station 110 (or other network node) may store the context associated with the suspended RRC connection between the UE 105 and base station 110. The stored context may also include information related to the PDCP connection as well.

At 114, UE 105 may send a message to request for the resumption of the suspended connection, in accordance with some example embodiments. For example, UE 105 may send an RRC connection resume request message to the base station 110.

Although 114 is requesting the connection resume to the same base station 110 at which the RRC connection was suspended, the connection resume request sent at 114 may be sent to other base stations, such as a new base station.

At 116, the base station 110 may send a connection resume message, in accordance with some example embodiments. For example, base station 110 may send, in response to message 114, an RRC connection resume message to the UE 105. In some example embodiments, the RRC connection resume message may be integrity-protected using a predetermined PDCP hyper frame number (HFN). This PDCP HEN maps to a PDCP COUNT value (e.g., 2³²−1 as noted above). This predetermined PDCP HFN allows the UE 105 and base station 110 to be in synchronization, even when the UE 105 moves to another, new base station after the initial suspension and RRC connection context retention. In the case of a new base station, the new base station may obtain, via signaling to the old base station or another network node, some of the context information but not the PDCP HFN or COUNT, so the use of the predetermined value provides little if any disruption to this signaling.

At 118, the UE 105 may verify, based on the predetermined PDCP HFN, the integrity of the received RRC connection resume message, in accordance with some example embodiments. If the verification is confirmed, then the UE may resume use of the RRC connection that was previously suspended. If the verification is not confirmed (e.g., the UE's expected PDCP COUNT and the PDCP COUNT used to integrity-protect the message 116 do not match), then the UE leaves the RRC connection and thus the previously suspended RRC connection is not re-used by the UE (in which case the UE may request an new RRC connection).

At 120, the UE may send, in accordance with some example embodiments, to the base station 110 an RRC connection resume complete message to indicate that the UE resumes use of the RRC connection that was previously suspended.

FIG. 2A depicts an example of a process 200 for handling PDCP COUNT, in accordance with some example embodiments. Process 200 is similar to process 100 in some respects, but in the case of process 200, the predetermined PDCP HFN is configured with all bits set to “1”. At 218, the UE 105 may request the lower layers to verify the integrity protection of the RRCConnectionResume message received at 216. For example, if the HE (or its lower layers) successfully verifies the integrity of the RRCConnectionResume message assuming the predetermined HFN, then the UE may enter, or resume, the RRC connected mode using the context for that connection. If the verification fails, then the UE does not resume the RRC connection and thus leaves the RRC connection. Table 2 below depicts an example RRC-specification text for 218.

TABLE 2 Reception of the RRCConnectionResume by the UE The UE shall: <...>  1>request lower layers to verify the integrity protection of the   RRCConnectionResume message, using HFN with all bits set to   “1” as defined in TS 36. 323, the previously configured   algorithm and the K_(RRCint) key;  1> if the integrity protection check of the RRCConnectionResume message fails:   2>>perform the actions upon leaving RRC_CONNECTED as  specified in 5.3.12, with release cause ‘other’, upon which the  procedure ends;

At 120, the UE may send, in accordance with some example embodiments, to the base station 110 an RRC connection resume complete message to indicate that the UE resumes use of the RRC connection that was previously suspended.

FIG. 2B depicts an example of a PDCP COUNT, in accordance with some example embodiments. In the example shown, the HFN may have all of its bits set to one. When a predetermined HFN value is used by both the UE and the base station, there will be no ambiguity on the used HFN and the PDCP COUNT between the UE and base station will be in synchronization (provided that also the PDCP SN is in synchronization) so the integrity verification performed on the message will pass. Synchronization of the PDCP SN can be achieved in different ways. As an example, the PDCP SN included in the header of the PDCP PDU containing the RRC connection resume message can be used. As another example, a predetermined value can be used also for the PDCP SN.

FIG. 3 depicts an example of a process 300 for handling PDCP count, in accordance with some example embodiments. FIG. 3 shows two base stations 110 and 310. The first base station 110 is where the RRC connection is suspended, while the second base station is where the RRC connection is resumed.

At 312, the RRC connection may be suspended between UE 105 and base station 110, in accordance with some example embodiments. Moreover, user plane traffic transmission via the uplink and/or the downlink may also be suspended. Moreover, the UE 105 and the base station 110 may store the context associated with the suspended RRC connection and/or PDCP context as well. At 314, UE 105 may send a RRC connection resume request message to another base station 310, in accordance with some example embodiments. At 316, the new base station 310 may send a connection resume message, in accordance with some example embodiments. The RRC connection resume message may be integrity-protected using a PDCP HFN that has a predetermined value, such as all bits set to “1”. In some example embodiments, the new base station 310 may obtain some of the context information regarding the suspended connection (e.g., from base station 110 or another node) but not the PDCP COUNT or SN. At 318, the UE 105 may verify the integrity of the received RRC connection resume message, in accordance with some example embodiments. This verification may be performed as described above at 118 and/or 218. At 320, the UE may send, in accordance with some example embodiments, to the base station 310 an RRC connection resume complete message to indicate that the UE resumes use of the RRC connection that was previously suspended.

In the example of process 300, the base station may receive a radio resource control connection resume request message sent by a user equipment. The base station may generate, in response to the received radio resource control connection resume request message, a radio resource control connection resume message. The base station may perform integrity protection of the radio resource connection resume message. The integrity protection may be performed based on a predetermined value of a packet data convergence protocol hyper frame number. The base station may also transmit to the user equipment the radio resource control connection resume message, wherein the radio resource control connection resume message is integrity protected.

FIG. 4 illustrates a block diagram of an apparatus 10, in accordance with some example embodiments. The apparatus 10 (or portions thereof) may be configured to provide a radio, such as user equipment 105 and/or a base station 110 and/or 310. The apparatus may be implemented as any device including a wireless device, a smart phone, a cell phone, a machine type communication device, a wireless sensor, a radio relay, an access point, and/or any other radio including a processor and memory based device.

In some example embodiments, apparatus 10 may be configured to support handling of a fixed or predetermined PDCP HFN as described herein.

The apparatus 10 may include at least one antenna 12 in communication with a transmitter 14 and a receiver 16. Alternatively transmit and receive antennas may be separate. The apparatus 10 may also include a processor 20 configured to provide signals to and receive signals from the transmitter and receiver, respectively, and to control the functioning of the apparatus. Processor 20 may be configured to control the functioning of the transmitter and receiver by effecting control signaling via electrical leads to the transmitter and receiver. Likewise, processor 20 may be configured to control other elements of apparatus 10 by effecting control signaling via electrical leads connecting processor 20 to the other elements, such as a display or a memory. The processor 20 may, for example, be embodied in a variety of ways including circuitry, at least one processing core, one or more microprocessors with accompanying digital signal processor(s), one or more processor(s) without an accompanying digital signal processor, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits (for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and/or the like), or some combination thereof. Accordingly, although illustrated in FIG. 4 as a single processor, in some example embodiments the processor 20 may comprise a plurality of processors or processing cores.

Signals sent and received by the processor 20 may include signaling information in accordance with an air interface standard of an applicable cellular system, and/or any number of different wireline or wireless networking techniques, comprising but not limited to Wi-Fi, wireless local access network (WLAN) techniques, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, and/or the like. In addition, these signals may include speech data, user generated data, user requested data, and/or the like.

The apparatus 10 may be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like. For example, the apparatus 10 and/or a cellular modem therein may be capable of operating in accordance with various first generation (1G) communication protocols, second generation (2G or 2.5G) communication protocols, third-generation (3G) communication protocols, fourth-generation (4G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (for example, session initiation protocol (SIP) and/or the like. For example, the apparatus 10 may be capable of operating in accordance with 2G wireless communication protocols IS-136, Time Division Multiple Access TDMA, Global System for Mobile communications, GSM, IS-95, Code Division Multiple Access, CDMA, and/or the like. In addition, for example, the apparatus 10 may be capable of operating in accordance with 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and/or the like. Further, for example, the apparatus 10 may be capable of operating in accordance with 3G wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), and/or the like. The apparatus 10 may be additionally capable of operating in accordance with 3.9G wireless communication protocols, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and/or the like. Additionally, for example, the apparatus 10 may be capable of operating in accordance with 4G wireless communication protocols, such as LTE Advanced, 5G, and/or the like as well as similar wireless communication protocols that may be subsequently developed.

It is understood that the processor 20 may include circuitry for implementing audio/video and logic functions of apparatus 10. For example, the processor 20 may comprise a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital-to-analog converter, and/or the like. Control and signal processing functions of the apparatus 10 may be allocated between these devices according to their respective capabilities. The processor 20 may additionally comprise an internal voice coder (VC) 20 a, an internal data modem (DM) 20 b, and/or the like. Further, the processor 20 may include functionality to operate one or more software programs, which may be stored in memory. In general, processor 20 and stored software instructions may be configured to cause apparatus 10 to perform actions. For example, processor 20 may be capable of operating a connectivity program, such as a web browser. The connectivity program may allow the apparatus 10 to transmit and receive web content, such as location-based content, according to a protocol, such as wireless application protocol, WAP, hypertext transfer protocol, HTTP, and/or the like.

Apparatus 10 may also comprise a user interface including, for example, an earphone or speaker 24, a ringer 22, a microphone 26, a display 28, a user input interface, and/or the like, which may be operationally coupled to the processor 20. The display 28 may, as noted above, include a touch sensitive display, where a user may touch and/or gesture to make selections, enter values, and/or the like. The processor 20 may also include user interface circuitry configured to control at least some functions of one or more elements of the user interface, such as the speaker 24, the ringer 22, the microphone 26, the display 28, and/or the like. The processor 20 and/or user interface circuitry comprising the processor 20 may be configured to control one or more functions of one or more elements of the user interface through computer program instructions, for example, software and/or firmware, stored on a memory accessible to the processor 20, for example, volatile memory 40, non-volatile memory 42, and/or the like. The apparatus 10 may include a battery for powering various circuits related to the mobile terminal, for example, a circuit to provide mechanical vibration as a detectable output. The user input interface may comprise devices allowing the apparatus 20 to receive data, such as a keypad 30 (which can be a virtual keyboard presented on display 28 or an externally coupled keyboard) and/or other input devices.

As shown in FIG. 4, apparatus 10 may also include one or more mechanisms for sharing and/or obtaining data. For example, the apparatus 10 may include a short-range radio frequency (RF) transceiver and/or interrogator 64, so data may be shared with and/or obtained from electronic devices in accordance with RF techniques. The apparatus 10 may include other short-range transceivers, such as an infrared (IR) transceiver 66, a Bluetooth™ (BT) transceiver 68 operating using Bluetooth™ wireless technology, a wireless universal serial bus (USB) transceiver 70, a Bluetooth™ Low Energy transceiver, a ZigBee transceiver, an ANT transceiver, a cellular device-to-device transceiver, a wireless local area link transceiver, and/or any other short-range radio technology. Apparatus 10 and, in particular, the short-range transceiver may be capable of transmitting data to and/or receiving data from electronic devices within the proximity of the apparatus, such as within 10 meters, for example. The apparatus 10 including the Wi-Fi or wireless local area networking modem may also be capable of transmitting and/or receiving data from electronic devices according to various wireless networking techniques, including 6LoWpan, Wi-Fi, Wi-Fi low power, WLAN techniques such as IEEE 802.11 techniques, IEEE 802.15 techniques, IEEE 802.16 techniques, and/or the like.

The apparatus 10 may comprise memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, an UICC, and/or the like, which may store information elements related to a mobile subscriber. In addition to the SIM, the apparatus 10 may include other removable and/or fixed memory. The apparatus 10 may include volatile memory 40 and/or non-volatile memory 42. For example, volatile memory 40 may include Random Access Memory (RAM) including dynamic and/or static RAM, on-chip or off-chip cache memory, and/or the like. Non-volatile memory 42, which may be embedded and/or removable, may include, for example, read-only memory, flash memory, magnetic storage devices, for example, hard disks, floppy disk drives, magnetic tape, optical disc drives and/or media, non-volatile random access memory (NVRAM), and/or the like. Like volatile memory 40, non-volatile memory 42 may include a cache area for temporary storage of data. At least part of the volatile and/or non-volatile memory may be embedded in processor 20. The memories may store one or more software programs, instructions, pieces of information, data, and/or the like which may be used by the apparatus for performing operations disclosed herein with respect to a user equipment and/or a base station (see, e.g., processes 100, 200, and/or 300). The memories may comprise an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying apparatus 10. The memories may comprise an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying apparatus 10. In the example embodiment, the processor 20 may be configured using computer code stored at memory 40 and/or 42 to control and/or provide one or more aspects disclosed herein with respect to the user equipment and/or a base station (see, for example, process 100, 200, and/or 300).

Some of the embodiments disclosed herein may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and/or hardware may reside on memory 40, the control apparatus 20, or electronic components, for example. In some example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a “computer-readable medium” may be any non-transitory media that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or data processor circuitry, with examples depicted at FIG. 4, computer-readable medium may comprise a non-transitory computer-readable storage medium that may be any media that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

Without in any way limiting the scope, interpretation, or application of the claims appearing below, a technical effect of one or more of the example embodiments disclosed herein is enhanced use of radio resources including RRC connection suspension and resume.

The subject matter described herein may be embodied in systems, apparatus, methods, and/or articles depending on the desired configuration. For example, the base stations and user equipment (or one or more components therein) and/or the processes described herein can be implemented using one or more of the following: a processor executing program code, an application-specific integrated circuit (ASIC), a digital signal processor (DSP), an embedded processor, a field programmable gate array (FPGA), and/or combinations thereof. These various implementations may include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device. These computer programs (also known as programs, software, software applications, applications, components, program code, or code) include machine instructions for a programmable processor, and may be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the term “computer-readable medium” refers to any computer program product, machine-readable medium, computer-readable storage medium, apparatus and/or device (for example, magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions. Similarly, systems are also described herein that may include a processor and a memory coupled to the processor. The memory may include one or more programs that cause the processor to perform one or more of the operations described herein.

Although a few variations have been described in detail above, other modifications or additions are possible. In particular, further features and/or variations may be provided in addition to those set forth herein. Moreover, the implementations described above may be directed to various combinations and subcombinations of the disclosed features and/or combinations and subcombinations of several further features disclosed above. Other embodiments may be within the scope of the following claims.

If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined. Although various aspects of some of the embodiments are set out in the independent claims, other aspects of some of the embodiments comprise other combinations of features from the described embodiments and/or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims. It is also noted herein that while the above describes example embodiments, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications that may be made without departing from the scope of some of the embodiments as defined in the appended claims. Other embodiments may be within the scope of the following claims. The term “based on” includes “based on at least.” The use of the phase “such as” means “such as for example” unless otherwise indicated. 

1. A method comprising: receiving, at a user equipment, a radio resource control connection resume message; verifying, at the user equipment, an integrity of the received radio resource control connection resume message, wherein the user equipment verifies the integrity based on a predetermined value of a packet data convergence protocol hyper frame number; and resuming, by the user equipment, use of a suspended radio resource control connection, when the integrity verification of the received radio resource connection resume message is passed successfully.
 2. The method of claim 1, further comprising: transmitting a radio resource control connection resume complete message when resuming use of the suspended connection.
 3. The method of claim 1, wherein the predetermined value is fixed to enable synchronization between the user equipment and a base station.
 4. The method of claim 1, wherein the predetermined value includes all bits set to a value of 1 or
 0. 5. The method of claim 1, wherein the use of the suspended radio resource control connection is resumed only when the integrity verification of the received radio resource connection resume message is passed successfully.
 6. The method of claim 1, wherein the base station is different than a base station where the user equipment suspended the radio resource control connection.
 7. (canceled)
 8. (canceled)
 9. (canceled)
 10. (canceled)
 11. (canceled)
 12. An apparatus comprising: at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receive a radio resource control connection resume message; verify an integrity of the received radio resource control connection resume message, wherein the apparatus verifies the integrity based on a predetermined value of a packet data convergence protocol hyper frame number; and resume use of a suspended radio resource control connection, when the integrity verification of the received radio resource connection resume message is passed successfully.
 13. The apparatus of claim 12, wherein the apparatus is further configured to at least transmit a radio resource control connection resume complete message when resuming use of the suspended connection.
 14. The apparatus of claim 12, wherein the predetermined value is fixed to enable synchronization between the apparatus and a base station.
 15. The apparatus of claim 12, wherein the predetermined value includes all bits set to a value of 1 or
 0. 16. The apparatus of claim 12, wherein the use of the suspended radio resource control connection is resumed only when the integrity verification of the received radio resource connection resume message is passed successfully.
 17. The apparatus of claim 12, wherein the base station is different than a base station where the apparatus suspended the radio resource control connection.
 18. The apparatus of claim 12, wherein the apparatus comprises a user equipment.
 19. An apparatus comprising: at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receive a radio resource control connection resume request message sent from a user equipment; generate, in response to the received radio resource control connection resume request message, a radio resource control connection resume message; perform integrity protection of the radio resource connection resume message, wherein the integrity protection is performed based on a predetermined value of a packet data convergence protocol hyper frame number; and transmit to the user equipment the radio resource control connection resume message, wherein the radio resource control connection resume message is integrity protected.
 20. The apparatus of claim 19, wherein the radio resource control connection resume request message is received to enable resumption of a suspended radio resource control connection.
 21. The apparatus of claim 19, wherein the apparatus comprises a base station.
 22. The apparatus of any of claim 21, wherein the predetermined value is fixed to enable synchronization between the user equipment and the base station.
 23. The apparatus of claim 19, wherein the predetermined value includes all bits set to a value of 1 or
 0. 24. The apparatus of claim 21, wherein the base station is different than a base station where the user equipment suspended the radio resource control connection.
 25. (canceled)
 26. (canceled)
 27. (canceled)
 28. (canceled)
 29. (canceled)
 30. (canceled)
 31. A non-transitory computer-readable storage medium including program code which when executed by at least one processor causes operations comprising: receiving, at a user equipment, a radio resource control connection resume message; verifying, at the user equipment, an integrity of the received radio resource control connection resume message, wherein the user equipment verifies the integrity based on a predetermined value of a packet data convergence protocol hyper frame number; and resuming, by the user equipment, use of a suspended radio resource control connection, when the integrity verification of the received radio resource connection resume message is passed successfully.
 32. (canceled) 